-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adjust invoker playbook to pull docker images when a prefix and tag is specified. #3680
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3680 +/- ##
==========================================
+ Coverage 74.92% 74.99% +0.06%
==========================================
Files 132 128 -4
Lines 6186 6075 -111
Branches 392 388 -4
==========================================
- Hits 4635 4556 -79
+ Misses 1551 1519 -32
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PG4 1715 ⏳
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PG2 3168 ⏳
@csantanapr made the changes we discussed on Slack to disentangle the image pulls from the docker registry. |
6261407
to
584fac4
Compare
0b1adb0
to
bb7b911
Compare
a53a47a
to
2b6faf9
Compare
3df97d4
to
5fb2565
Compare
@dgrove-oss I think you'll need to review this now as its scope as widened a little. I did checked the kube deployment and I think the change is compatible but will appreciate your input. With the latest changes, runtime images are pulled from the given docker registry for runtimes (default is dockerhub) which is now allowed to be different from the docker.registry; the latter is now strictly used for the system components. It is possible to skip the pulling of images entirely:
or with
|
@ddragosd this may also be relevant to docker-compose although I haven't checked that deployment yet. |
Some caveats with this change: building new runtime images for local testing means:
FYI @remore @akrabat @sciabarracom since you will be affected by this change if we accept it. |
3996c6d
to
fdfde1d
Compare
Looks like this would be straightforward for kube. We'd need to update the copies of runtime.json and tweak values.yaml and the various deployment templates for the pods to reflect the change in environment variables. |
71e2691
to
f6e18b1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Remove default runtime prefix and tag; the runtimes.json file should fully specify these. Remove docker.{registry,prefix,tax} entanglement with runtimes as these are used for the system images not the runtimes. Optionally specify a runtimes.registry to pull images from there instead of dockerhub.
…pache#3680) Remove default runtime prefix and tag; the runtimes.json file should fully specify these. Remove docker.{registry,prefix,tax} entanglement with runtimes as these are used for the system images not the runtimes. Optionally specify a runtimes.registry to pull images from there instead of dockerhub.
Description
The invoker playbook ignores an image prefix when pre-fetching the blackbox images. This patch splits the blackbox tasks so that ones that do not have a prefix may be skipped (as today), but those that specify a prefix are always pulled, using the specified prefix in the image name.
Fixes #3679.
Related issue and scope
My changes affect the following components
Types of changes
Checklist: